didn't check everything just briefly skimmed through, but already few questions:

• in a5243f4 a publish was made, but i don't see the updated versions here, what is the meaning of this commit? Was the publish reverted?
• why the versions in the mentioned commit are already "final" and not alpha or beta if the work on this PR still not finished?
• there's no need to publish to npmjs if you need to test something locally, you can use yarn pack to create needed artifacts and then install those via yarn install
• if you want to test not only locally please release alpha or beta version and not final

Hey, I did not actually publish anything yet, just let it run through once to check if all works with the newest version, thus the versions also have not alpha beta or anything applied to them. Would revert/rerun the publish again once it is ready

Hey @deathmaz @kalievsky, will you guys have some time to check this soon?

Hi @ChristianPraiss cannot promise when exactly but will check at some point, want to also test it in one of my projects. Have you tried it on real projects on your side?

Soo, I updated it and gave it a round of testing. It's a slight bit stricter overall (tested on https://github.com/convidera/partnerlink), reporting some no-unused-vars and no-explicit-any warnings, but i guess those are very valid rules anyway. @jhoefker @deathmaz.

@ChristianPraiss i tried it on my project and in some places eslint reported errors where it shouldn't:

Details

in all defineEmits declared as:

const emit = defineEmits<{(e: 'close'): void,
  (e: 'success', payload: AppDataTaskApplicationFeedFeedItemResource): void
}>();

things like e and payload reported as unused vars. There's no error if emits are defined this way:

const emit = defineEmits<{
  close: [],
  success: [payload: AppDataTaskApplicationFeedFeedItemResource]
}>();

Because those are not errors and the syntax is a valid vue3 syntax, imo it's better to not report those things as errors if possible.

The rest of the reported issues i got mostly about no-explicit-any, which if needed could be changed on per project basis and i'm fine with it

Hey, thx for testing it out! Will check what can be done about the rule, will see if there is a vue-specific version or if the rule params have an option to fix this.